TMap is an approach that can be applied in all test situations and in combination with any system development method. It offers the tester a range of elements for his test, such as test design techniques, test infrastructure, test strategy, phasing, test organisation, test tools, etc. Depending on the situation, the tester selects the TMap elements that he will deploy. There are situations in which only a limited number of elements need to be used; but in others he will have to use the whole range of elements. This makes TMap an adaptive method, which in this context is defined as: "Adaptive is the ability to split up an element into sub-elements that, in a different combination, result in a new, valuable element for the specific situation."

The adaptiveness of TMap is not focused on a specific aspect of the method, but is embedded throughout the method. Adaptiveness is more than just being able to respond to the changing environment. It is also being able to leverage the change to the benefit of testing. This means that TMap can be used in every situation and that TMap can be used in a changing situation. In the course of projects and testing, changes may occur that have an impact on earlier agreements. TMap offers the elements to deal with such changes.

TMap’s adaptiveness can be summarised in four adaptiveness properties:

• Respond to changes
• (Re)use products and processes
• Learn from experiences
• Try before use

These properties are explained in further detail below.

Respond to changes

Adaptiveness starts with determining the changes and responding to them. In TMap, this happens from the very beginning in the earliest activities of the (master) test plan. When determining and taking stock of the assignment, obtaining insight into the environment in which the test is executed and establishing possible changes play a major part. This is precisely where the basis is created for the further elaboration and implementation of the method. Which test levels, test types, phases, and tools are used and how? But it is not limited to these activities. The test strategy and associated planning are defined in close consultation with the client. If the test strategy and derived estimate and planning are not acceptable to the client, the plan is adapted. This emphatic gives the client control of the test process, enabling him to manage based on the balance between result and risk on the one hand and time and cost on the other. Such feedback is provided throughout the testing programme, and in the control phase, the test manager may also decide to adapt certain aspects of the test plan in consultation with the client.

(Re)use products and processes

Being able to use products and processes quickly is a requirement for adaptiveness. TMap offers this possibility, among other things thanks to the large quantity of tools included in the form of test design techniques, checklists, templates, etc. These can be found in this method and on www.tmap.net. In addition to use, reuse plays an important part. The emphasis in this respect lies in the Completion phase, where the activities are defined to identify what can be reused and how it can be optimally preserved. TMap offers various forms of a permanent test organisation for the organisational anchoring of the reuse of products and processes.

Learn from experience

As a method, TMap offers the space to learn and apply what was used. Therefore the activity evaluating the test process is incorporated into the test process. An other important instrument is the use of metrics. For the test process, metrics on the quality of the test object and the progress and quality of the test process are extremely important. They are used to manage the test process, justify the test recommendations, and compare systems or test processes. Metrics are also important to improve the test process through assessing the consequences of certain improvement measures.

Try before use

TMap offers room to try something before it is actually used. The main instruments here are the activities relating to the intake. The intake of the test basis (using a testability review), of the test infrastructure, and of the test object allow one to try first before actually using.

Implementing TMap does not mean that everything in the method should be used without question. Another form of trying before using is therefore ‘customising’ TMap to fit a specific situation. A selection can be made from all of the TMap elements to achieve this. After the approach, customised to the situation, has been tried out (‘pilot’), it can be rolled out in the organisation.

For many situations, ‘customising’ TMap has already been done. The specific TMap approach for a certain situation (known under the name ‘expansion’) can be found on www.tmap.net and in the TMap Test Topics book [Koomen, 2005].